Supervising and recovering software components associated with medical diagnostics instruments

ABSTRACT

A system for applying a recovery mechanism to a network of medical diagnostics instruments is provided herein. The system includes the following: a plurality of medical diagnostics instruments, each associated with a network connected component; a plurality of communication modules, each associated with a corresponding one of the plurality of network connected components, wherein each one of the plurality of communication modules is arranged to report on malfunctioning components that are network connected with the corresponding component, and a recovery module, configured to: (i) obtain reports from the communication modules; (ii) re-establish the malfunctioning components; and (iii) notify all communication modules of the re-establishment of the malfunctioning components, wherein the communication modules are further configured to re-establish connection between the corresponding components and the re-established components.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present invention is a Continuation application of U.S. patent application Ser. No. 13/311,971, filed Dec. 6, 2011, which is incorporated by reference for all purposes.

BACKGROUND

1. Technical Field

The present invention relates to the field of monitoring software components and more specifically, to the monitoring and recovering of software components associated with medical diagnostics instruments.

2. Discussion of Related Art

There is an ongoing trend of more and more diagnostics instruments becoming connected via a communication network for both monitoring and managing purposes. One of the characteristics of the data being processed is that it is usually private medical data. This requirement imposes, inter alia, data security measures. Additionally, as diagnostics instruments may be required around the clock, it would be advantageous to reduce mean time between failures of the diagnostics instrument.

BRIEF SUMMARY

One aspect of the invention provides a system for applying a recovery mechanism to a network of medical diagnostics instruments. The system may include the following features: a plurality of medical diagnostics instruments, each associated with a network connected component; a plurality of communication modules, each associated with a corresponding one of the plurality of network connected computer software components, wherein each one of the plurality of communication modules is arranged to report on malfunctioning computer software components that are network connected with the corresponding component, and a recovery module, configured to: (i) obtain reports from the communication modules; (ii) re-establish the malfunctioning computer software components; and (iii) notify all communication modules of the re-establishment of the malfunctioning computer software components, wherein each communication module is further configured to re-establish a connection between the one of the plurality of the computer software components and the re-established computer software components.

These, additional, and/or other aspects and/or advantages of the present invention are: set forth in the detailed description which follows; possibly inferable from the detailed description; and/or learnable by practice of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be more readily understood from the detailed description of embodiments thereof made in conjunction with the accompanying drawings of which:

FIG. 1A is a high level schematic block diagram of a recovery mechanism in an environment of networked components according to some embodiments of the invention;

FIG. 1B is a high level schematic and detailed block diagram of the recovery mechanism in an environment of networked components, according to some embodiments of the invention;

FIGS. 2A and 2B are sequence diagrams illustrating aspects according to some embodiments of the invention;

FIG. 3A and 3B are sequence diagrams illustrating other aspects according to some embodiments of the invention;

FIG. 4 is a block diagram illustrating establishing a connection between each other, to some embodiments of the invention;

FIG. 5 is sequence diagram illustrating communication between various layers in two components that are supervised by CMS, to some embodiments of the invention;

FIG. 6 is a sequence diagram illustrating startup of modules in a component, when a component receives a request for service, to some embodiments of the invention; and

FIG. 7 is a block diagram illustrating communication class library, to some embodiments of the invention.

DETAILED DESCRIPTION

Before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of the components set forth in the following description or illustrated in the drawings. The invention is applicable to other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.

For a better understanding of the invention, the usages of the following terms in the present disclosure are defined in a non-limiting manner:

The terms “component” and “software component,” as used herein in this application, is defined as a software application comprised of business logic, a communication layer, a subscription manager and a service component.

The term “network,” as used herein in this application, is defined as an infrastructure that enables an exchange of data between two or more nodes, such as the aforementioned components. In a non-limiting private case, the two or more nodes may reside on a single computer.

The term “communication module,” as used herein in this application, is defined as the module that is associated with a component and responsible for: (i) reporting failure of other components that are network connected to the component; and (ii) re-establish connection between a re-established component and the corresponding component.

The term “recovery module,” as used herein in this application, is defined as the module that is responsible for the activity status of components in the system.

The term “Configuration Manager Service (CMS),” as used herein in this application, is defined as the collection of procedures used to manage workflow in a collaborative environment. These procedures may be manual or computer-based.

The term “Window Communication Foundation (WCF),” as used herein in this application, is defined as an Application Programming Interface (API) in the .NET framework for building connected, service-oriented applications.

The term “WCF façade,” as used herein in this application, is defined as a service that allows a WCF client to access the components that are being serviced.

The term “IsAlive poll,” as used herein in this application, is defined as a message that is sent from a client of a component in CMS to the communication module of its corresponding component in order to check the activity status of the component.

The term “Watchdog Mechanism,” as used herein in this application, is defined as the mechanism that is responsible for checking the activity status of components every specified period of time.

The term “business logic module,” as used herein in this application, is defined as the module in a component that actually provides services to other components and requests services from other services.

The term “exception,” as used herein in this application, is defined as the message thrown by a program when the normal flowchart conditions were not met.

The term “Method call,” as used herein in this application, is defined as the request from a component to perform a task.

FIG. 1A is a high level schematic block diagram of a recovery mechanism 100 in an environment of networked components 90A-90D, according to some embodiments of the invention. Recovery mechanism 100 may include a plurality of communication modules 110A-110D, each associated with a corresponding one of networked components 90A-90D. Each communication module 110, for example, communication module 110A, is arranged to report on malfunctioning components, for example, components 90B and 90C that are networked with communication module 110A via corresponding component 90A. Additionally, recovery mechanism 100 may further include a recovery module 120 that is arranged to: (i) obtain reports from the communication modules 110A-110D; (ii) re-establish malfunctioning components for example, components 90B and 90C; and (iii) notify all communication modules 110A-110D of the re-establishment of the malfunctioning components (e.g., components 90B and 90C).

In response to the re-establishing carried out by recovery mechanism 100 operation, and continuing with the example above, a notification to the communication modules 110A-110D may be sent and communication modules 110A-110D in turn may re-establish connections between their corresponding components 90A and 90D and the re-established components 90B and 90C. Additionally, the re-establishing of the malfunctioning components 90B and 90C by the recovery module 120 may be carried out according to a specified priority list 130 of components being recovery priority.

FIG. 1B illustrates a more detailed expression of recovery mechanism implemented, in a non-limiting example within a context of a Configuration Manager Service (CMS) 80, which manages the following: (i) information of the component 150; (ii) general configuration 152; (iii) info of clients and priority 154; (iv) application of subscriber information 156; and (v) pool information 158. The connection between communication modules 110A-110F and its corresponding component 90A-90F may be implemented via WCF façades 85A-85F that may provide a simplified interface to components 90A-90F. The aforementioned recovery process may be triggered to operate by (i) the CMS 80; (ii) any component 90A-90F; and/or (iii) communication module 110F-110F.

Table 1 illustrates a non-limiting example for priorities and associated sets of components 90A-9GF to be recovered are provided herein.

Malfunctioning Priority Recover Component list Components 90A Critical All 90B Medium 90B, 90C 90C Medium 90C, 90B 90D Low 90D 90E Low 90E 90F High 90F, 90B, 90C

Consistent with some embodiments of the present invention the recovery may be carried out by re-establishing malfunctioning components 90A-90F group-wise, according to specified inter-dependencies among networked components 90A-90F, to quickly recover functionality associated with the groups of components 90A-90F.

FIG. 2A illustrates an IsAlive poll 200A carried out by CMS 80. CMS 80 keeps a client 84 for every component in the system (84A, 84B, and so forth), either locally or remotely. Watchdog mechanism 82 may check the operation of the components (not shown here) every specified period of time. For example, CMS 80 may send an IsAlive poll every x minutes, with x configurable via a configuration. Client 84A in CMS 80 may receive an exception from the service that indicated malfunctioning component.

FIG. 2B illustrates the activation 200B of recovery module by one of communication modules 110A, according to one embodiment. Any component 90, for example component 90B, may throw an exception to component 90A, as a response to a query 113, namely a request for service from the component 90B. Consequently, communication module 110A may identify that the associated component 90A received an exception which was thrown by component 90B, and notifies business logic module 114 its communication layer 112 namely, communication module 110A, that it received an exception, as an indication of a malfunctioning component 90B.

Then, communication layer 112 may use its corresponding CMS client 84 to notify CMS 80 that the specific service provider, namely the malfunctioning component 90B, threw an exception. Then, CMS 80 may start recovery mechanism 100.

As a result, recovery module 120 may attempt to reload malfunctioning component 90B that has crashed. In case recovery module 120 failed to reload crashed component 90B and component 90B was specified as critical in priority list 130, recovery module 120 activates a termination operation to component 90B.

Further, recovery mechanism 100 may facilitate priority based recovery mechanism, using a priority list 130 of components. Recovery mechanism 100 may support distribution of: (i) local components that are running on the same computer; and (ii) distributed components that are running on a network.

FIG. 3A is a sequence diagram illustrating an activation sequence 300A of WCF environment by CMS 80, according to some embodiments of the invention. CMS 80 creates a client 116 that activates 302 WCF façade 85. Then WCF façade 85 creates an instance of a business logic module 114 and an instance of a communication module 110. Consequently, communication module (not shown here) creates a client 116 to communicate with CMS client (not shown here) to exchange information. Then, communication module 110 may perform logging provider proxy 306 and creates an instance of logging client in WCF façade service 85.

FIG. 3B is a sequence diagram illustrating a termination sequence 300B of WCF environment by CMS 80, according to some embodiments of the invention. Termination operation 304 starts with CMS 80 sending a termination message 310 to communication layer 112. In response communication module (not shown here) in communication layer 112 sends termination message 310 to business logic module 114. Business logic module 114 sends response to WCF façade service 85 when it is ready to terminate via its communication layer 112. Then WCF façade service 85 sends ready-to-be-terminated message 118 to communication module 110. In response, communication module 110 sends component-is-ready-to-be-terminated message 312 to CMS 80.

FIG. 4 is a block diagram illustrating two components establishing a connection between each other, to some embodiments of the invention. Each component may consist of several clients to provide services to other components. For example, a component 90A may provide services to another component 90B via a client 402B and component 90B may provide services to component 90A via a client 402A. Further, each component may include a client to CMS (not shown here), for example, CMS client 404A in component 90A and CMS client 404B in component 90B. Component 90A may retrieve configuration information via client 404A and component 90B may retrieve configuration information via CMS client 404B. An example of the configuration information that may be retrieved is endpoint of service of other components.

FIG. 5 is a sequence diagram illustrating a subscription process between two components 90A and 90B that are supervised by CMS 80. The subscription process is performed via various layers, according to some embodiments of the invention. The subscription process may start when component 90A requires a service from component 90B. Component 90A may send a registration request 502 message to CMS 80 and may retrieve endpoints of the subscription manager that refers to the service required using a client for CMS 80. Then, CMS 80 creates an event with registration request 504 to communication module (not shown here) of component 90B in communication layer 112. The registration request 504 refers to the selected service. The type of request message sent is a callback method. Then, in component 90B communication module (not shown here) may reopen the subscription manager module 520 and may send a registration request 506 to the subscription manager module 520. The type of request message sent is a Method call. In response, subscription manager module 520 may send a notification of approval or denial 508 to client 402B in component 90A. The notification may include an endpoint of the selected service. The type of message sent is a callback method. In case subscription manager sent an approval message to component 90A, component 90A opens subscriber client 510. The type of request message sent is a callback method.

FIG. 6 is a sequence diagram illustrating startup of modules in a component, when a component receives a request for service, to some embodiments of the invention. CMS 80 may send a method call to activate subscription manager module 520. CMS 80 sends a method call to activate WCF façade service 85. In response, WCF façade service 85 may call for service default constructor 618. The service default constructor 618 may create an instance of business logic module 114 by sending a regular method call. Further WCF façade service 85 may create an instance in communication layer 112 and pass the business logic instance 114 as an argument for future usage.

Then, the communication layer 112 may create a client 650 to communicate with the CMS 80. The communication layer 112 may use this client 650 to retrieve information from the CMS 80. The information that may be retrieved is: (i) subscription information with endpoints of all subscription manager services that the component may need to register to; (ii) client information with endpoints of all services that the component may be authorized to attach to. Based on the information retrieved 608 from the subscription manager module 520 taken from the CMS 80, the communication layer 112 may create a client 624 and may send subscription requests 626. Further, the communication layer 112 may create a regular client 622 for all services based on information about the clients taken from the CMS 80. Then, the communication layer 112 may call to initialize a method in the WCF façade 85 for additional initializations. Then, the communication layer (not shown here) may notify the CMS 80 that the component was loaded.

FIG. 7 is a block diagram illustrating a communication class library, according to some embodiments of the invention. The communication class library allows each component to communicate with the CMS (not shown here) to: (1) retrieve information about a client that the component wishes to open; (2) get notification(s) in case another process crashed; and (3) get notification(s) of a component reload and recreate a client for reloaded component and register to its events. The communication class library allows each component to register the component to other process events and open clients upon other process services.

In the above description, an embodiment is an example or implementation of the invention. The various appearances of “one embodiment”, “an embodiment” or “some embodiments” do not necessarily all refer to the same embodiments.

Although various features of the invention may be described in the context of a single embodiment, the features may also be provided separately or in any suitable combination. Conversely, although the invention may be described herein in the context of separate embodiments for clarity, the invention may also be implemented in a single embodiment.

Furthermore, it is to be understood that the invention can be carried out or practiced in various ways and that the invention can be implemented in embodiments other than the ones outlined in the description above. In particular, the invention is not limited to those diagrams or to the corresponding descriptions. For example, flow need not move through each illustrated box or state, or in exactly the same order as illustrated and described. Methodologies described herein may be implemented by various means depending upon applications according to particular features or examples. For example, such methodologies may be implemented in hardware, firmware, software, discrete/fixed logic circuitry, any combination thereof, and so forth. In a hardware or logic circuitry implementation, for example, a processing unit may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, electronic devices, other devices or units designed to perform the functions described herein, or combinations thereof, just to name a few examples.

For a firmware or software implementation, the methodologies may be implemented with modules (e.g., procedures, functions, etc.) having instructions that perform the functions described herein. Any non-transitory computer- and/or machine-readable medium embodying instructions may be used in implementing the methodologies described herein. For example, software codes from a computer program product or other source may be stored in a memory and executed by a processor. Memory may be implemented within the processor or external to the processor. As used herein the term “memory” refers to any type of long term, short term, volatile, nonvolatile, or other memory and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored. In at least some implementations, one or more portions of the herein described storage media may store signals representative of data or information as expressed by a particular state of the storage media. For example, an electronic signal representative of data or information may be “stored” in a portion of the storage media (e.g., memory) by affecting or changing the state of such portions of the storage media to represent data or information as binary information (e.g., ones and zeros). As such, in a particular implementation, such a change of state of the portion of the storage media to store a signal representative of data or information constitutes a transformation of storage media to a different state or thing.

Meanings of technical and scientific terms used herein are to be commonly understood as by one of ordinary skill in the art to which the invention belongs, unless otherwise defined.

While the invention has been described with respect to a limited number of embodiments, these should not be construed as limitations on the scope of the invention, but rather as exemplifications of some of the preferred embodiments. Other possible variations, modifications, and applications are also within the scope of the invention. Accordingly, the scope of the invention should not be limited by what has thus far been described, but by the appended claims and their legal equivalents. 

What is claimed is:
 1. A system for applying a recovery mechanism to a plurality of computer software components that control medical diagnostics, the system comprising: a plurality of medical diagnostics instruments, each associated with a computer software component; a plurality of communication modules, wherein each one of the plurality of communication modules is associated with a corresponding one of the plurality of the computer software components, and configured to report on the corresponding one of the computer software components; and a recovery module, configured to: (i) obtain reports from the plurality of communication modules, the reports enabling a determination of whether at least one computer software component is malfunctioning; (ii) reload the at least one malfunctioning computer software component according to a priority of the at least one malfunctioning computer software component, and (iii) notify all communication modules of the reloading of the at least one malfunctioning computer software component; wherein each one of the plurality of communication modules is further configured to re-establish a connection between the corresponding one of the plurality of the computer software components and the at least one reloaded computer software component.
 2. The system according to claim 1, wherein the recovery module is configured to reload the at least one malfunctioning computer software component of a first medical diagnostics instrument by creating, at a communication layer, a client for providing a service to another computer software component of a second medical diagnostic instrument.
 3. The system according to claim 1, wherein the recovery module is further configured to reload critical malfunctioning computer software components prior to other malfunctioning computer software components, according to specified criteria.
 4. The system according to claim 1, wherein the recovery module is further configured to reload the malfunctioning computer software components groupwise, according to specified inter-dependencies among network-connected components.
 5. The system according to claim 1, wherein the recovery module is further configured to terminate an operation of one or more network-connected computer software components upon failure of a reloading thereof.
 6. The system according to claim 1, wherein the recovery module is further configured to carry out the notifying based on a predefined priority order of computer software components.
 7. The system according to claim 1, wherein the recovery module is configured to reload the at least one malfunctioning computer software component according to the priority of the at least one malfunctioning computer software component by determining an indication of an order by which the at least one malfunctioning computer software component is to be reloaded.
 8. A method of applying a recovery mechanism to software components that control medical diagnostics instruments, the method comprising: monitoring a plurality of medical diagnostics instruments, each medical diagnostic instrument associated with a software component via a plurality of communication modules; obtaining a report from a communication module of the plurality of communication modules, the report enabling a determination of whether at least one software component is malfunctioning; determining, from an obtained report, an occurrence of a malfunctioning of the at least one software component; reloading the at least one malfunctioning software component after analyzing the obtained report, wherein the reloading of the at least one malfunctioning software component is performed according to a priority of the at least one malfunctioning software component; notifying all communication modules of the plurality of communication modules of the reloading of the at least one malfunctioning software component; and re-establishing a connection between the software components and the at least one reloaded software component, via the plurality of communication modules.
 9. The method according to claim 8, wherein the reloading a malfunctioning software component of a first medical diagnostics instrument comprises creating, at a communication layer, a client for providing a service to another software component of a second medical diagnostic instrument.
 10. The method according to claim 8, wherein the reloading of the at least one malfunctioning software component comprises reloading a plurality of malfunctioning software components, such that reloading one of the plurality of malfunctioning software components occurs prior to reloading another of the plurality of malfunctioning software components, according to specified criteria.
 11. The method according to claim 8, wherein the reloading of the at least one malfunctioning software component is carried out according to specified inter-dependencies among network-connected software components.
 12. The method according to claim 8, further comprising terminating an operation of one or more network-connected software components upon failure of a reloading thereof.
 13. The method according to claim 8, wherein the notifying is carried out based on a predefined priority order of software components.
 14. The method according to claim 8, wherein the priority of the at least one malfunctioning software component comprises an indication of an order by which the at least one malfunctioning software component is to be reloaded.
 15. A computer program product embodied on a non-transitory computer-readable medium, the computer program product comprising computer code for: monitoring software components associated with a medical instrument, each medical instrument associated with a software component via a plurality of communication modules; obtaining a report from a communication module of the plurality of communication modules, the report enabling a determination of whether at least one software component is malfunctioning; determining, from the obtained report, an occurrence of a malfunctioning of the at least one software component; reloading the at least one malfunctioning software component after analyzing the obtained report, wherein the reloading the at least one malfunctioning software component is performed according to a priority of at least one malfunctioning software component; notifying all communication modules of the plurality of communication modules of the reloading of the at least one malfunctioning software component; and re-establishing a connection between the software components and the at least one reloaded software component, via the plurality of communication modules.
 16. The computer program product according to claim 15, wherein computer code for reloading a malfunctioning software component of a first medical diagnostics instrument comprises computer code for creating, at a communication layer, a client for providing a service to another software component of a second medical diagnostic instrument.
 17. The computer program product according to claim 15, wherein the computer code for the reloading of the at least one malfunctioning software component is carried out such that the at least one malfunctioning software component is reloaded prior to other malfunctioning software components, according to specified criteria.
 18. The computer program product according to claim 15, wherein the computer code for the reloading of the at least one malfunctioning software component is carried out group-wise, according to specified inter-dependencies among network-connected software components.
 19. The computer program product according to claim 15, further comprising computer code for terminating an operation of one or more network-connected software components upon failure of a reloading thereof.
 20. The computer program product according to claim 15, wherein the computer code for the notifying comprises computer code for carrying out the notifying based on a predefined priority order of software components. 